-
Notifications
You must be signed in to change notification settings - Fork 48
[14/n] tensor engine {handle_cast, handle} -> handle #491
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: gh/zdevito/30/base
Are you sure you want to change the base?
Conversation
We unified the message handling logic in rust, so we can keep that unification for the python bindings. We keep the handle_cast variant, rename it handle. We provide a definition for cast coordinates even when a message wasn't cast: the message is considered to be the rank of a zero dimension shape. Differential Revision: [D78061501](https://our.internmc.facebook.com/intern/diff/D78061501/) [ghstack-poisoned]
We unified the message handling logic in rust, so we can keep that unification for the python bindings. We keep the handle_cast variant, rename it handle. We provide a definition for cast coordinates even when a message wasn't cast: the message is considered to be the rank of a zero dimension shape. Differential Revision: [D78061501](https://our.internmc.facebook.com/intern/diff/D78061501/) ghstack-source-id: 295416054 Pull Request resolved: #491
This pull request was exported from Phabricator. Differential Revision: D78061501 |
We unified the message handling logic in rust, so we can keep that unification for the python bindings. We keep the handle_cast variant, rename it handle. We provide a definition for cast coordinates even when a message wasn't cast: the message is considered to be the rank of a zero dimension shape. Differential Revision: [D78061501](https://our.internmc.facebook.com/intern/diff/D78061501/) [ghstack-poisoned]
Pull Request resolved: #491 We unified the message handling logic in rust, so we can keep that unification for the python bindings. We keep the handle_cast variant, rename it handle. We provide a definition for cast coordinates even when a message wasn't cast: the message is considered to be the rank of a zero dimension shape. ghstack-source-id: 295529039 @exported-using-ghexport Differential Revision: [D78061501](https://our.internmc.facebook.com/intern/diff/D78061501/)
This pull request was exported from Phabricator. Differential Revision: D78061501 |
We unified the message handling logic in rust, so we can keep that unification for the python bindings. We keep the handle_cast variant, rename it handle. We provide a definition for cast coordinates even when a message wasn't cast: the message is considered to be the rank of a zero dimension shape. Differential Revision: [D78061501](https://our.internmc.facebook.com/intern/diff/D78061501/) [ghstack-poisoned]
Pull Request resolved: #491 We unified the message handling logic in rust, so we can keep that unification for the python bindings. We keep the handle_cast variant, rename it handle. We provide a definition for cast coordinates even when a message wasn't cast: the message is considered to be the rank of a zero dimension shape. ghstack-source-id: 295544965 @exported-using-ghexport Differential Revision: [D78061501](https://our.internmc.facebook.com/intern/diff/D78061501/)
This pull request was exported from Phabricator. Differential Revision: D78061501 |
We unified the message handling logic in rust, so we can keep that unification for the python bindings. We keep the handle_cast variant, rename it handle. We provide a definition for cast coordinates even when a message wasn't cast: the message is considered to be the rank of a zero dimension shape. Differential Revision: [D78061501](https://our.internmc.facebook.com/intern/diff/D78061501/) [ghstack-poisoned]
Pull Request resolved: #491 We unified the message handling logic in rust, so we can keep that unification for the python bindings. We keep the handle_cast variant, rename it handle. We provide a definition for cast coordinates even when a message wasn't cast: the message is considered to be the rank of a zero dimension shape. ghstack-source-id: 295544965 @exported-using-ghexport Differential Revision: [D78061501](https://our.internmc.facebook.com/intern/diff/D78061501/)
This pull request was exported from Phabricator. Differential Revision: D78061501 |
We unified the message handling logic in rust, so we can keep that unification for the python bindings. We keep the handle_cast variant, rename it handle. We provide a definition for cast coordinates even when a message wasn't cast: the message is considered to be the rank of a zero dimension shape. Differential Revision: [D78061501](https://our.internmc.facebook.com/intern/diff/D78061501/) [ghstack-poisoned]
Pull Request resolved: #491 We unified the message handling logic in rust, so we can keep that unification for the python bindings. We keep the handle_cast variant, rename it handle. We provide a definition for cast coordinates even when a message wasn't cast: the message is considered to be the rank of a zero dimension shape. ghstack-source-id: 295545965 @exported-using-ghexport Differential Revision: [D78061501](https://our.internmc.facebook.com/intern/diff/D78061501/)
This pull request was exported from Phabricator. Differential Revision: D78061501 |
We unified the message handling logic in rust, so we can keep that unification for the python bindings. We keep the handle_cast variant, rename it handle. We provide a definition for cast coordinates even when a message wasn't cast: the message is considered to be the rank of a zero dimension shape. Differential Revision: [D78061501](https://our.internmc.facebook.com/intern/diff/D78061501/) [ghstack-poisoned]
Pull Request resolved: #491 We unified the message handling logic in rust, so we can keep that unification for the python bindings. We keep the handle_cast variant, rename it handle. We provide a definition for cast coordinates even when a message wasn't cast: the message is considered to be the rank of a zero dimension shape. ghstack-source-id: 295545965 @exported-using-ghexport Differential Revision: [D78061501](https://our.internmc.facebook.com/intern/diff/D78061501/)
This pull request was exported from Phabricator. Differential Revision: D78061501 |
We unified the message handling logic in rust, so we can keep that unification for the python bindings. We keep the handle_cast variant, rename it handle. We provide a definition for cast coordinates even when a message wasn't cast: the message is considered to be the rank of a zero dimension shape. Differential Revision: [D78061501](https://our.internmc.facebook.com/intern/diff/D78061501/) [ghstack-poisoned]
Pull Request resolved: #491 We unified the message handling logic in rust, so we can keep that unification for the python bindings. We keep the handle_cast variant, rename it handle. We provide a definition for cast coordinates even when a message wasn't cast: the message is considered to be the rank of a zero dimension shape. ghstack-source-id: 295550756 @exported-using-ghexport Differential Revision: [D78061501](https://our.internmc.facebook.com/intern/diff/D78061501/)
This pull request was exported from Phabricator. Differential Revision: D78061501 |
Stack from ghstack (oldest at bottom):
We unified the message handling logic in rust, so we can keep that unification for the python bindings. We keep the handle_cast variant, rename it handle.
We provide a definition for cast coordinates even when a message wasn't cast: the message is considered to be the rank of a zero dimension shape.
Differential Revision: D78061501